• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    downstream splitter synchronization pattern protected by header error control on a ten gigabyte passive optical network. an apparatus is provided, which comprises an optical terminal line (tof) configured to couple a plurality of distributors downstream to the onuss, wherein each of the downstream distributors comprises a plurality of fronts for correcting codeword errors (fec) and a plurality of additional non-fec encoded bytes that comprise the synchronization information that is protected by a header code error control (hec). an apparatus is provided, which comprises a processing unit configured to provide control data, user data, or both in a plurality of code words fec in a downstream splitter and provide a physical synchronization sequence (psync), a super structure splitter, and a passive optical network identifier (pon-id) structure of a plurality of additional encoded non-fec bytes in the downstream splitter, and a transmission unit configured to transmit the code words fec and the added non-encoded bytes close in the downstream splitter within a 125 microsecond window.
    公开号:BR112012014620B1
    申请号:R112012014620-3
    申请日:2010-12-06
    公开日:2021-03-30
    发明作者:Yuanqiu Luo；J. Frank Effenberger
    申请人:Huawei Technologies Co., Ltd；
    IPC主号:
    专利说明:

    Field of the Invention
    The present invention relates to communications technologies and, in particular, a Standard Ten-Gigabit Passive Optical Network Frame Synchronization Standard Protected by Header Error Control. Background of the Invention
    A passive optical network (PON) is a system for providing “last mile” network access (final connectivity stretch). PON is a point-to-multiple point network comprised of an optical line terminal (OLT) at the telephone exchange, an optical distribution network (ODN) and a plurality of optical network units (ONUs) at the consumer's premises. In some PON systems, such as Gigabit PON (GPON) systems, normal flow data is broadcast at around 2.5 Gigabits per second (Gbps), while reverse flow data is transmitted at around 1.25 Gbps. However, PON systems' bandwidth capacity is expected to increase as service demands increase. To match increased demand for services, some emerging PON systems, such as next generation access systems (NGA), are being reconfigured to transport data frames with increased reliability and efficiency at higher bandwidths, for example, at around ten Gbps. Summary of the Invention
    In one embodiment, the exhibit includes an apparatus comprising an OLT configured to couple a plurality of ONUs and transmit a plurality of frames of normal flow to the ONUs, where each of the frames of normal flow comprises a plurality of code words error correction (FEC) and a plurality of additional non-FEC encoded bytes that comprise synchronization information that is protected by a header error control (HEC) code.
    In another embodiment, the display includes an apparatus comprising a processing unit configured to dispose of control data, user data or both in a plurality of FEC code words in a normal flow frame and to have a physical synchronization sequence (PSync), a subframe structure and a passive optical network identifier (PON-ID) structure in a plurality of additional non-FEC encoded bytes in the normal flow frame, and a transmission unit configured to transmit the code words additional FEC encoded bytes in the normal flow frame in a 125 microsecond window.
    In yet another modality, the exhibition includes a method comprising the implementation, in a UN, of a synchronization state machine that comprises a Hunting State, a Pre-synchronization State and a Synchronization State for a plurality of frames of normal flow, wherein each of the normal flow frames comprises a physical synchronization block (PSBd) comprising a physical synchronization pattern (PSync), a subframe structure and a PON-ID structure, wherein the subframe structure comprises a subframe counter and a first HEC protecting the subframe structure, and wherein the PON-ID structure comprises a PON-ID and a second HEC protecting the PON-ID structure.
    These and other resources will be understood more clearly from the detailed description below taken in conjunction with the associated drawings and claims. Brief Description of Drawings
    For a more complete understanding of this exhibition, a reference is now made to the brief description below, taken in relation to the associated drawings and to the detailed description, in which equal reference numbers represent equal parts. Figure 1 is a schematic diagram of a PON modality. Figure 2 is a schematic diagram of a frame modality. Figure 3 is a schematic diagram of an embodiment of a portion of a frame. Figure 4 is a schematic diagram of an embodiment of another portion of a frame. Figure 5 is a schematic diagram of an embodiment of a synchronization state machine. Figure 6 is a flow chart of an embodiment of a PON framing method. Figure 7 is a schematic diagram of an embodiment of an apparatus configured to implement a PON framing method. Figure 8 is a schematic diagram of a modality of a general purpose computer system. Detailed Description of the Modalities
    It should be understood at the outset that, although an illustrative implementation of one or more modalities is provided below, the systems and / or methods exposed can be implemented using any number of techniques, currently known or existing. The exposure should not be limited in any way to the illustrative implementations, drawings and techniques illustrated below, including the sample projects and implementations illustrated and described here, but may be modified in the scope of the appended claims along with their full scope of equivalent.
    In PON systems, errors in a plurality of frames can be corrected using an FEC scheme. According to the FEC scheme, the transmitted frames may comprise a plurality of FEC code words, which may comprise a plurality of data blocks and parity blocks. Each number of blocks that correspond to an FEC code word can then be aligned or "locked" using a "state machine", for example, in a buffer, a framer or a memory location in a UN or a OLT. The FEC code word can be locked after detecting one of its data blocks and parity blocks one by one and verifying that the block sequence matches the expected block sequence of an FEC code word. Otherwise, when a block is detected as out of sequence, the process can be restarted on the second block in the block sequence to detect and lock the correct block sequence.
    A system and method for supporting transmission synchronization and error detection / correction in PON systems, such as 10 Gigabit PONs (XGPONs), are exposed here. The system and method use a framing mechanism that supports the FEC scheme and provides transmission synchronization at the PON. The frames can be transmitted in a plurality of transmission windows, for example, time periods of around 125 microseconds, where each transmission window can comprise an integer multiple of FEC code words for error detection / correction. The transmission window can also comprise additional or extra bytes that can be used for a transmission synchronization. Extra bytes may comprise frame synchronization and / or time synchronization and may not be encoded with FEC (for example, not protected by FEC) and therefore cannot be manipulated by the FEC scheme. In fact, the extra bytes can also comprise an HEC encoding, which can provide error detection / correction for the synchronization information in the frames. Figure 1 illustrates a modality of a PON 100. The PON 100 comprises an OLT 110, a plurality of ONUs 120 and an ODN 13 0, which can be coupled to OLT 110 and ONUs 120. The PON 100 can be a network that does not require any active components for data distribution between OLT 110 and ONUs 120. In fact, PON 100 can use passive optical components on ODN 130 for data distribution between OLT 110 and ONUs 120 The PON 100 can be NGA systems, such as ten gigabit GPONs (or XGPONs), which can have a normal flow bandwidth of around ten Gbps, and an opposite flow bandwidth of at least around 2.5 Gbps. Other examples of suitable PONs 100 include the asynchronous transfer mode PON (APON) and broadband PON (BPON) defined by the International Telecommunication Union (ITU-T) Standard Telecommunication Union (ITU-T) G.983, GPON defined by the ITU-T G.984 standard, the Ethernet PON (EPON) defined by the Institute of Electrical and Electronics Engineers (IEEE) 802.3ah standard, the 10 Gigabit EPON, as described in the IEEE 802.3av standard, and the multiplexed PON with wavelength division (WDM) (WPON), all of which are incorporated herein by reference, as if reproduced in their entirety.
    In one embodiment, OLT 110 can be any device that is configured to communicate with ONUs 120 and another network (not shown). Specifically, OLT 110 can act as an intermediary between the other network and ONUs 120. For example, OLT 110 can forward data received from the network to ONUs 120, and forward data received from ONUs 120 to the other network. Although the specific configuration of the OLT 110 may vary, depending on the type of PON 100, in one embodiment, the OLT 110 can comprise a transmitter and a receiver. When the other network is using a network protocol, such as Ethernet or synchronous optical network connection (SONET) / synchronous digital hierarchy (SDH), which is different from the PON protocol used on the PON 100, the OLT 110 can comprise a converter which converts the network protocol into the PON protocol. The OLT converter 110 can also convert the PON protocol to the network protocol. The OLT 110 can typically be located in a central location, such as a telephone exchange, but it can be located in the same way in other locations.
    In one embodiment, the ONUs 12 0 can be any devices that are configured to communicate with the OLT 110 and a consumer or user (not shown). Specifically, ONUs 120 can act as an intermediary between OLT 110 and the consumer. For example, ONUs 120 can forward data received from OLT 110 to the consumer, and forward data received from the consumer to OLT 110. Although the specific configuration of ONUs 120 may vary, depending on the type of PON 100, in In one embodiment, the ONUs 120 can comprise an optical transmitter configured to send optical signals to the OLT 110 and an optical receiver configured to receive optical signals from the OLT 110. Additionally, the ONUs 120 can comprise a converter that converts the optical signal into electrical signals to the consumer, such as signals in the Ethernet protocol, and a second transmitter and / or receiver that can send and / or receive electrical signals to a consumer device. In some modalities, ONUs 120 and optical network terminals (ONTs) are similar, so the terms are used interchangeably here. ONUs typically can also be located in distributed locations, such as consumer facilities, but they can be located in other locations in the same way.
    In one embodiment, ODN 13 0 may be a data distribution system, which may comprise fiber optic cables, couplers, splitters, distributors and / or other equipment. In one embodiment, fiber optic cables, couplers, splitters, distributors and / or other equipment can be passive optical components. Specifically, fiber optic cables, couplers, splitters, distributors and / or other equipment can be components that do not require any power for the distribution of data signals between OLT 110 and ONUs 120. Alternatively, ODN 130 can comprise a or a plurality of processing equipment, such as optical amplifiers. ODN 130 can typically extend from OLT 110 to ONUs 12 0 in a branch configuration, as shown in Figure 1, but alternatively it can be configured in any other point to multiple point configuration.
    In one modality, OLT 110, ONUs 120 or both can be configured to implement an FEC scheme to control or reduce transmission errors. As part of the FEC scheme, the data can be combined with an error correction code, which can comprise redundant data, before being transmitted. For example, the data and an error correction code can be encapsulated or framed in an FEC code word, which can be received and decoded by another PON component. In some embodiments, the FEC codeword can comprise the error correction code and can be transmitted with the data without modifying the data bits. When the error correction code is received, at least some of the errors in the transmitted data, such as bit errors, can be detected and corrected, without the need for additional data transmission. Transmitting the error correction code in addition to the data can consume at least part of the channel bandwidth, and hence can reduce the available bandwidth for the data. However, the FEC scheme can be used for error detection, instead of a dedicated indirect channel for reducing the complexity of the error detection scheme, cost or both.
    The FEC scheme can comprise a state machine model, which can be used to lock an FEC code word, for example, to determine whether a plurality of received blocks representing the FEC code word is properly aligned or in a correct sequence. Locking the FEC code word or checking the alignment of FEC blocks may be necessary to obtain the data and error correction code correctly. For example, OLT 110, ONUs 120 or both may comprise an FEC processor, which may be hardware, such as a circuit, or software that implements the state machine model. The FEC processor can be coupled to the corresponding receivers and / or framers on OLT 110 or ONUs 120, and can use an analog to digital conversion, modulation and demodulation, line coding and decoding, or combinations thereof. The FEC code word comprising the received blocks can also be locked in a memory location or a buffer coupled to the FEC processor and the receiver.
    Typically, normal flow data in PON systems can be transmitted in a plurality of GPON transmission container frames (GTC), for example, in a GTC layer, in a plurality of corresponding fixed time windows, for example , of around 125 microseconds. A GTC board can comprise a normal flow control physical block (PCBd) and a GTC payload (for example, user data) that cannot comprise time or time of day (ToD) information. However, for the establishment of synchronization of PON transmissions, a ToD information or any other synchronization information may be required in the transmitted frames. In one embodiment, the OLT 110 can be configured to transmit a ToD information and / or any other synchronization information to the UN (s) 120, for example, in a normal flow frame in a corresponding transmission. The normal flow frame can also support the FEC scheme for error detection and correction. Therefore, the transmission window may comprise FEC code words, which may comprise data and an error correction code, and time or ToD information. Specifically, the transmission window can comprise a multiple integer of FEC codewords and a plurality of extra or additional bytes that cannot be encoded with FEC and, therefore, cannot be manipulated or protected from errors using the FEC. The extra or additional bytes can be used for the provision of time information (for example, ToD) and / or synchronization for PON transmissions, and can also comprise an HEC encoding that can be used for the detection and / or the correction of any errors in the synchronization data.
    For example, OLT 110 can transmit normal stream data in a plurality of XGPON transmission container frames (XGTC) in a corresponding time window of around 125 microseconds or any fixed length time window. The XGTC frame (and the corresponding time window) can comprise a payload comprising FEC code words, for example, around 627 FEC code words using a Reed-Solomon (RS) FEC encoding ( 248, x) (for example, x is equal to around 216 and / or around 232). In addition, the XGTC frame (and the corresponding time window) may comprise additional bytes (for example, on the PCBd), for example, around 24 bytes, which comprise synchronization and / or time synchronization data and an encoding of HEC, as described in detail below. Figure 2 illustrates an embodiment of a frame 200, which can comprise control data encoded with FEC and / or user and synchronization information encoded not with FEC. For example, frame 200 can correspond to a frame of GTC or XGTC, for example, of normal flow from OLT 110 to a UN 120, and can be transmitted in a fixed time window. Frame 200 may comprise a first portion 210 and a second portion 211. The first portion 210 may correspond to a GTC or XGTC PCBd or a header and may comprise timing or synchronization information, such as a PSync pattern, a ToD, another time and / or a picture synchronization information or combinations of them. Specifically, the timing or synchronization information may not be encoded with FEC and may be associated with an HEC encoding in the first portion 210, which can be used for the detection / correction of a plurality of bit errors that may occur in the first portion 210. The first portion 210 is described in more detail below. In one embodiment, frame 200 may correspond to a frame of GTC or XGTC that is encoded using RS (248, x) and, thus, the first portion 210 may comprise around 24 bytes. Although the first portion 210 precedes the second portion 211 in figure 2, in other embodiments, the first portion 210 may be located at other locations in frame 200, such as subsequently to the second portion 211.
    The second portion 211 can correspond to a GTC or XGTC payload and can comprise a plurality of code words that can be encoded with FEC. For example, second portion 211 may comprise an integer multiple of FEC code words. The payload of GTC or XGTC can comprise a normal flow of payload length (Plend) 212, a reverse flow bandwidth map (US BWmap) 214, at least one administration and maintenance field, physical layer operations (PLOAM) 216 and payload 218. Plend 212 can comprise a plurality of subfields, including a length B (Blen) and a cyclic redundancy check (CRC). Blen can indicate the length of the US BWmap 214, for example, in bytes. The CRC can be used to check for errors in the received frame 200, for example, at UN 120. For example, frame 2 00 can be discarded when the CRC fails. In some PON systems that support asynchronous transfer mode (ATM) communications, subfields may also include a subfield of length A (Alen) that indicates the length of an ATM payload, which may comprise a portion of frame 2 00. US BWmap 214 may comprise an arrangement of blocks or subfields, each of which may comprise a single bandwidth allocation for an individual transmission (TC) container, which can be used for managing the bandwidth allocation. reverse flow band in the GTC layer. The TC can be a transport entity in the GTC layer, which can be configured to transfer higher layer information from an input to an output, for example, from the OLT to the UN. Each block in BWmap 214 can comprise a plurality of subfields, such as an allocation identifier (Alloc-ID), Flag type indicators, a Start Time (SStart), a Stop Time (SStop), a CRC, or combinations of the same.
    PLOAM 216 fields can comprise a PLOAM message, which can be sent from the OLT to the UN and include alarms related to operations, administration and maintenance (OAM) or threshold exceeded alerts triggered by system events. The PLOAM 216 field can comprise a plurality of subfields, such as a ONU identifier (ONU-ID), a message identifier (Message-ID), message data and a CRC. The UN-ID can comprise an address, which can be assigned to one of the UNs and can be used by that UN to detect its intended message. The Message-ID can indicate the type of the PLOAM message and the message data can comprise the payload of the PLOAM message. The CRC can be used to check for the presence of errors in the received PLOAM message. For example, the PLOAM message can be discarded when the CRC fails. Table 200 can comprise different PLOAMs 216 that correspond to different ONUs, which can be indicated by different ONU-IDs. Payload 218 can comprise broadcast data (e.g., user data). For example, payload 218 may comprise a GPON encapsulation method (GEM) payload. Figure 3 illustrates an embodiment of a frame portion 300 that can comprise non-FEC encoded synchronization information, such as in a normal flow GTC or XGTC frame. For example, frame portion 300 may correspond to first portion 210 of frame 200. Frame portion 300 may comprise a PSync field 311, a ToD field in seconds (ToD-Sec) 315 and a ToD field in nanoseconds (ToD-Nanosec) 321. In one embodiment, the frame portion 300 can comprise around 24 bytes, where each of the PSync 311 field, the ToD-Sec 315 field and the ToD field in nanosecond 321 can comprise around eight bytes. In addition, each of the PSync 311 fields, the ToD-Sec 315 fields and the ToD-Nanosec 321 fields can comprise an HEC coding that can be used to detect / correct errors in the corresponding field.
    The PSync 311 field can comprise a PSync 312 standard and an HEC 314 field. The PSync 312 standard can be used in a UN, for example, in a data frame coupled to a receiver, for detecting the beginning of normal flow frame portion 300 (or frame 200) and establishing synchronization accordingly. For example, the PSync 312 pattern can correspond to a fixed pattern that cannot be shuffled. The HEC 314 field can provide error detection and correction for the PSync 311. field. For example, the HEC 314 field can comprise a plurality of bits that correspond to a Bose and Ray-Chaudhuri (BCH) code with a generator polynomial and a single parity bit. In one embodiment, the PSync 312 standard can comprise around 51 bits and the HEC 314 field can comprise around 13 bits.
    The ToD-Sec 315 field can comprise a 316 Second field, a Reserved (Rev) 318 field and a second HEC 320 field. The 316 Second field can comprise an integer portion of the ToD associated with the frame in units of seconds, and the Reserved field 318 may be reserved or may not be used. The second HEC 320 field can be configured to be substantially similar to HEC 314 and can provide error detection and correction for the ToD-Sec 315 field. In one embodiment, the 316 Second field can comprise around 4 8 bits, the Reserved field 318 can comprise around three bits, and the second HEC 320 field can comprise around 13 bits.
    The ToD-Nanosec 321 field can comprise a Nanosecond field 322, a second Reservado (Rev) field 324 and a third HEC 326 field. The Nanosecond field 322 can comprise a fractional portion of the ToD associated with the frame in units of nanoseconds, and the second Reserved field 324 may be reserved or may not be used. The third HEC 32 6 can be configured substantially similar to HEC 314 and can provide error detection and correction for the ToD-Nanosec 321 field. In one embodiment, the Nanosecond 322 field can comprise around 32 bits, the second field of Reservado 324 can comprise around 19 bits, and the third field of HEC 326 can comprise around 13 bits. Figure 4 illustrates another embodiment of a frame portion 400 that can comprise non-FEC encoded synchronization information. For example, frame portion 400 may correspond to a PSBd in a normal flow GTC or XGTC frame. The PSBd 410 can comprise a PSync pattern 412, a subframe structure 414 and a PON-ID 420 structure. In one embodiment, the frame portion 200 or the PSBd can comprise around 24 bytes, where each of the PSync standard 412, subframe structure 414 and PON-ID 420 structure can comprise around eight bytes. In addition, each of the subframe structure 414 and the PON-ID 420 structure can comprise an HEC coding that can be used for the detection / correction of errors in the corresponding field.
    The PSync 412 standard can be used to detect the beginning of the PSBd in the frame and can comprise around 64 bits. The PSync 412 standard can be used by the UN for frame alignment at the normal flow frame border. The PSync 412 pattern can comprise a fixed pattern, such as 0xC5E5 1840 FD59 BB49. Subframe structure 414 may comprise a subframe counter 416 and an HEC code 418. Subframe counter 416 may correspond to about 51 most significant bits of subframe structure 414 and may specify a sequence of normal stream frames transmitted . For each normal flow frame (XGTC or GTC), the subframe counter 416 can comprise a value greater than the normal flow frame transmitted previously. When subframe counter 416 reaches a maximum value, a subsequent subframe counter 416 in a subsequent normal flow frame can be set to around zero. The HEC code 418 can correspond to around 13 less significant bits of subframe structure 414 and can be configured substantially similar to the HEC fields described above. The HEC 418 code can be a combination of a BCH code that operates on about the starting 63 bits of the frame header and a single parity bit.
    The PON-ID 420 structure can comprise a PON-ID 422 and a second HEC 424 code. PON-ID 422 can correspond to about 51 bits of the PON-ID 42 0 structure and the HEC code can correspond around the remaining 13 bits. PON-ID 422 can be regulated by OLT and used by the UN to detect protection switching events or to generate a security key. The second HEC code 424 can be configured substantially similar to the HEC fields described above. Specifically, the HEC code 418 can be used for the detection / correction of errors in the subframe counter 416 and the second HEC code 4 24 can be used for the detection / correction of errors in PON-ID 422.
    Since the synchronization information can be encapsulated in a plurality of extra bytes in the normal flow frames that cannot be encoded with FEC, the HEC code can be added to the synchronization information in the extra bytes, as described in the frame portion. 3 00 or in the frame portion 4 00, for the provision of sufficient and / or acceptable error detection / correction capacity for the UN synchronization information. This HEC coding scheme can provide efficient error detection / correction in a plurality of cases. For example, when the UN is in a context of rapid inactivity, the UN may re-lock every certain period of time (for example, each time around 10 microseconds) for the OLT. As such, multiple errors can occur in the extra bytes not encoded with FEC (for example, around 24 bytes) in the case of a false crash. However, there can be a substantially high probability that errors will be avoided or accounted for using the HEC encoding in the extra bytes.
    For example, in the case of a bit error rate (BER) of around le-03 in normal PON stream transmission, an HEC code comprising around 13 bits in a field of around eight bytes corresponding in the normal flow frame, such as the HEC fields described above, can be used for detecting up to around three bit errors and correcting up to around two bit errors in the corresponding eight byte field. In this case, the probability of obtaining around three bit errors in a corresponding field of around eight bytes after using the HEC scheme can be substantially small, for example, equal to around 0.0039 percent . The three bit errors can be detected, but they cannot be corrected using the HEC scheme. Also, the probability of obtaining around four bit errors or more in the corresponding field of around eight bytes after using the HEC scheme can be equal to around 0.0001 percent. However, the chances of obtaining around two bits of error or less if using the HEC scheme can be substantially high, for example, equal to around 99.996 percent. The two bit errors can be detected and corrected using the HEC scheme.
    During the frame locking process, the frame can be efficiently validated against at least two correctable PSync standards in the received frame. For example, the UN can successfully lock the normal flow frame if at least two PSync patterns, such as the PSync 312 pattern, have been received and detected correctly, for example, in the two subsequent fields of around eight bytes. The probability of detecting two consecutive PSync patterns correctly using two corresponding HEC codes, such as the HEC 314 field, can be substantially high, for example, equal to around 99.996 percent raised to the second power or around 99.992 percent (e.g. 99.996% * 2 = 99.992 percent). Thus, using around 24 extra bytes that comprise an HEC encoding, as described in figures 2, 3 and 4, the UN can be allowed to successfully lock the normal flow frame to a substantially normal level of certainty (for example, around 99.992 percent).
    In addition, the chance of establishing a false lock at the UN may require the detection of two subsequent PSync fields that comprise the same fixed pattern (for example, comprise the same bit errors). A situation like this can most likely occur when there could be around four bit errors in both PSync standards. The probability of receiving them around four bits in two around the corresponding 64 bits (or around 24 extra bytes in the frame) can be calculated by the binomial coefficient which is one of 64 * 63 * 62 * 61 / (1 * 2 * 3 * 4) or around 1 / 653,376 percent. As such, the chance of obtaining two false PSync standards can be equal to around 0.0001 percent raised to the second power or around 1 to 12 percent. Thus, the chance of establishing a false lock can be almost equal to the product (1/635376) x (le-12) or around 5e-19 percent, which can be negligible. In a context of relatively fast retraction inactivity, for example, around every ten microseconds, this situation can correspond to a false lock occurring at around 1.7 and 6 seconds and can be tolerated. Figure 5 illustrates a modality of a synchronization state machine 500, which can be used, for example, by the UN, for the synchronization of a normal flow transmitted frame, such as frame 200. The synchronization state machine 500 can use a PSync pattern in the normal flow frame that cannot be FEC encoded, such as the PSync 312 pattern or the PSync 412 pattern. The PSync pattern can be located in a portion of the normal flow frame, such as PSBd, in the frame portion 300 or in the first portion 210. In some embodiments, the PSync pattern can be protected by an HEC code, such as the HEC 314 field.
    The synchronization status machine 500 can be implemented by the UN, for example, using software, hardware or both. The synchronization status machine 5 00 can start in a Hunting State 510, where a search for the PSync pattern in all possible alignments (for example, bit and / or byte alignments) can be performed. If a correct PSync pattern is found, then the sync state machine 500 can transition to a Pre-Sync State 520, where a search for a second PSync pattern that follows the last PSync pattern detected by a length fixed time (for example, for around 125 microseconds) can be performed. If the second PSync pattern is not found successfully in Pre-Sync State 520, then the Sync State Machine 500 can return from Pre-Sync State 520 back to Hunting State 510. If a second PSync pattern is successfully found in Pre-Sync State 520, then Sync State Machine 500 can transition to Sync State 530. If Sync State 530 is reached, the Sync State Machine synchronization status 500 may declare successful synchronization of the normal flow frame, and frame processing can subsequently begin. In one embodiment, if the UN detects M consecutive incorrect PSync fields or patterns (M is an integer), then the sync state machine 500 can declare an unsuccessful sync from the normal flow frame and return back to the state of Hunting 510. For example, M can be equal to around five. Figure 6 illustrates a modality of a framing method 600, which can be used, for example, by the OLT, to frame a normal flow frame, such as an XGTC or GTC frame, before sending the flow frame. normal for the UN (s). The normal flow frame can comprise control and / or user data that can be encoded with FEC and synchronization and / or time data that cannot be encoded with FEC. However, at least some of the synchronization and / or time data can be protected in the normal flow frame using HEC encoding. In block 610, control data, user data, or both (control / user data) can be encapsulated in an integer multiple of FEC code words in the normal flow frame. For example, user / control data can be converted into a plurality of FEC code words that can be located in the payload portion of XGTC or GTC. For example, user / control data may comprise Plend, a plurality of fields or PLOAM messages, a user payload or combinations thereof.
    In block 620, the synchronization / time data and the corresponding HEC code can be encapsulated in a plurality of remaining bytes without an FEC encoding in the normal flow frame. For example, the synchronization data may be located in the PCBd or PSBd portion of XGTC or GTC. The synchronization / time data may comprise a plurality of synchronization elements, such as a PSync pattern, a ToD, a PON-ID or combinations thereof. The synchronization / time data may also comprise a corresponding HEC code or field for at least some of the synchronization / time elements, such as ToD, PON-ID and / or the PSync standard. In block 630, the FEC code words that comprise the control / user data and the remaining bytes that comprise the synchronization / time data and the corresponding HEC code can be transmitted, for example, to the UN (s) ( s) in the normal flow chart. Method 600 can then end. Figure 7 illustrates a modality of an apparatus 700 that can be configured to implement the framing method of PON 600. The apparatus may comprise a processing unit 710 and a transmission unit transmission unit 720 that can be configured for the implementation of the method 600. For example, processing unit 710 and transmission unit 720 may correspond to hardware, firmware and / or software installed to run on the hardware. The processing unit 710 can be configured to arrange control data, user data or both in a plurality of FEC code words in a normal flow frame and to arrange synchronization information in a plurality of bytes not encoded with additional FECs in the normal flow chart, as described in steps 610 and 620 above. The synchronization information can comprise the PSync 311 field, the ToD-Sec 315 field and the ToD-Nanosec 321 field. Alternatively, the synchronization information can comprise the PSync pattern 412, the subframe structure 414 and the structure PON-ID 420. The processing unit 710 can then forward the additional FEC code words and non-FEC encoded bytes to the transmission unit 720. The transmission unit 720 can be configured for the transmission of the code words of FEC and additional non-FEC encoded bytes in the normal flow frame in a fixed time window, for example, at around 125 microseconds. In other embodiments, processing unit 710 and transmission unit 720 can be combined into a single component or can comprise a plurality of subcomponents that can implement method 600.
    The network components described above can be implemented in any general purpose network component, such as a computer or a network component with sufficient processing power, memory resources and network transmission rate capability to handle the load. necessary work force imposed on him. Figure 8 illustrates a typical general purpose network component 800 suitable for implementing one or more modalities of the components exposed here. The network component 800 includes an 802 processor (which can be referred to as a central processing unit or CPU) that is communicating with memory devices including secondary storage 804, read-only memory (ROM) 806, memory random access (RAM) 808, input / output (I / O) devices 810 and network connectivity devices 812. The 802 processor can be implemented as one or more CPU chips or be part of one or more specific integrated circuits application (ASICs).
    Secondary storage 804 is typically comprised of one or more disk drives or tape drives, and is used for non-volatile data storage and as an up-and-over data storage device, if RAM 808 is not large or enough to keep all work data. Secondary storage 804 can be used to store programs that are loaded in RAM 808 when these programs are selected to run. ROM 806 is a non-volatile memory device that typically has a small memory capacity compared to the larger memory capacity of secondary storage 804. RAM 808 is used for storing volatile data and perhaps for storing instructions . Access to ROM 806 and RAM 8 08 is typically faster than secondary storage 804.
    At least one modality is exposed and variations, combinations and / or modifications of the modality (s) and / or features of the modality (s) made by a person having common knowledge in the technique are within the scope of the exhibition . Alternative modalities that result from the combination, integration and / or omission of resources from the modality (s) are also within the scope of the exhibition. When numerical ranges or limitations are expressly stated, those expressed ranges or limitations should be understood to include iterative ranges or limitations of similar magnitude falling into the ranges or limitations expressly stated (for example, from around 1 to around 10 included 2, 3, 4, etc.; more than 0.10 includes 0.11, 0.12, 0.13, etc.). For example, whenever a numerical range with a lower limit, Ri, and an upper limit, Ru, is shown, any number falling in the range will be specifically shown. In particular, the following numbers in the range are specifically shown: R = Ri + k * (Ru - Ri), where k is a variable ranging from 1 percent to 100 percent, with an increase of 1 percent, that is is, k is 1 percent, 2 percent, 3 percent, 4 percent, 5 percent, .. , 50 percent, 51 percent, 52 percent,. .., 95 percent, 96 percent, 97 percent, 98 percent, 99 percent, or 100 percent. Furthermore, any numerical range defined by two R numbers as defined above is also specifically exposed. The use of the term "optionally" with respect to any element of a claim means that the element is required or, alternatively, the element is not required, both alternatives being within the scope of the claim. The use of broader terms, such as comprises, includes and having, is to be understood as providing support for narrower terms, such as consisting of, consisting essentially of, and substantially understood by. Accordingly, the scope of protection is not limited by the description set out above, but is defined by the claims that follow, that scope including all equivalents of the subject in question to the claims. Each and every claim is incorporated as an additional statement in the specification and the claims are modalities of the present statement. The discussion of a reference in the exhibition is not an admission that is prior art, especially any reference that has a publication date after the priority date of this application. The exhibition of all patents, patent applications and publications cited in the exhibition is hereby incorporated as a reference, to the extent that they provide details of example, procedure or other supplementary details to the exhibition.
    Although several modalities have been provided in the present exhibition, it should be understood that the systems and methods exposed could be realized in many other specific ways, without departing from the spirit or the scope of the present exhibition. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given here. For example, the various elements or components can be combined or integrated into another system or certain features can be omitted or not implemented.
    In addition, techniques, systems, subsystems and methods described and illustrated in the various modalities as discrete or separate can be combined or integrated with other systems, modules, techniques or methods, without departing from the scope of the present exhibition. Other items shown or discussed as coupled or coupled directly or in communication with each other can be coupled indirectly or be in communication through some interface, device or intermediate component, whether electrically, mechanically or otherwise. Other examples of changes, substitutions and alterations can be evaluated by someone skilled in the art and could be done without deviating from the spirit and scope exposed here.
    权利要求:
    Claims (13)
    [0001]
    1. Apparatus characterized by the fact that it comprises: an optical line terminal (OLT) (110) configured for coupling to a plurality of optical network units (ONUs) (120) and for the transmission of a plurality of frames of normal flow for ONUs (120), where each of the normal flow frames comprises a plurality of anticipated error correction (FEC) code words and a plurality of additional bytes that comprise synchronization information that is protected by a header error control (HEC); where the FEC code words are encoded using a Reed-Solomon (RS) FEC encoding (248, x), where x is equal to 216 or 232, where each of the normal flow frames comprises an integer number of FEC code words, and where the plurality of additional bytes are 24 bytes in length.
    [0002]
    2. Apparatus according to claim 1, characterized in that the synchronization information comprises an eight-byte physical synchronization sequence (412), an eight-byte subframe structure (414) and a network identifier structure passive optics (PON-ID) of eight bytes (420).
    [0003]
    3. Apparatus according to claim 2, characterized by the fact that the HEC code comprises a first 13-bit HEC code (418) and a second 13-bit HEC code (424), wherein the structure of subframe (414) comprises a 51 bit subframe counter (416) and the first HEC code (418), wherein the PON-ID structure (420) comprises a 51 bit PON-ID (422) and the second HEC code (424), where the first HEC code (418) protects the subframe counter (416), and where the second HEC code (424) protects the PON-ID (422).
    [0004]
    4. Apparatus according to claim 1, characterized by the fact that the synchronization information comprises a physical synchronization field (PSync), a time of day in seconds field (ToD-Sec) and a time of day field in nanoseconds (ToD-Nanosec), and each of the PSync fields, the ToD-Sec field and the ToD-Nanosec field is eight bytes long and protected by the HEC code.
    [0005]
    5. Apparatus according to claim 4, characterized by the fact that the PSync field comprises a 51-bit PSync sequence which is protected by a first 13-bit HEC code, in which the ToD-Section field The control panel comprises a 48-bit Second field, and a three-bit reserved field, which is protected by a second 13-bit HEC code, and the ToD-Nanosec field comprises a 32-nanosecond field. bits, and a 19-bit reserved field, which is protected by a third 13-bit HEC field.
    [0006]
    6. Apparatus according to any one of claims 1 to 5, characterized by the fact that each of the frames of normal flow is transmitted in a fixed time window, and in which the number of FEC code words is equal to 627 FEC code words.
    [0007]
    7. Apparatus, according to claim 1, characterized by the fact that the HEC code is a Bose and Ray-Chaudhuri (BCH) code with a generating polynomial and a single parity bit.
    [0008]
    8. Apparatus according to claim 1, characterized by the fact that the normal flow frame is a 10 gigabit passive optical network (XGTC) transmission frame comprising a normal flow physical synchronization block (PSBd ) and an XGTC payload, where the PSBd comprises 24 non-FEC encoded bytes, where the PSBd comprises the synchronization information, and where the XGTC payload comprises the FEC code words.
    [0009]
    9. Method characterized by the fact that it comprises: the implementation, in an optical network unit (UN) (120), of a state synchronization machine that comprises a State of Hunting, a State of Pre-synchronization and a State of Synchronization for a plurality of normal flow frames, where each of the normal flow frames comprises a plurality of anticipated error correction (FEC) code words and a physical synchronization block (PSBd) comprising a physical synchronization pattern ( PSync), a subframe structure and a passive optical network identifier (PON-ID) structure, in which the FEC code words are encoded using a Reed-Solomon (RS) FEC encoding (248, x ), where x is equal to 216 or 232; wherein the subframe structure comprises a subframe counter and a first header error control (HEC) protecting the subframe structure, and where the PON-ID structure comprises a PON-ID and a second HEC protecting the subframe structure. PON-ID, where the subframe counter is 51 bits long and the HEC is 13 bits long, and where the PSBd is 24 bytes long, and where the PON-ID is 51 bits long and the second HEC is 13 bits long.
    [0010]
    10. Method, according to claim 9, characterized by the fact that the FEC does not protect the PSBd.
    [0011]
    11. Method, according to claim 9, characterized by the fact that the synchronization state machine starts in the Hunting State and seeks the PSync pattern in all possible alignments.
    [0012]
    12. Method, according to claim 9, characterized by the fact that, once the correct PSync standard has been found, the UN (120) transitions to the Pre-Synchronization State and looks for another PSync standard , which follows the latest PSync standard for 125 microseconds.
    [0013]
    13. Method, according to claim 12, characterized by the fact that, if the PSync standard is successfully verified, the UN (120) transitions to the Synchronization State, and in which, if a PSync standard is found, the UN (120) transits back to the Hunting State.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112012014620B1|2021-03-30|APPARATUS AND METHOD FOR STANDARD SYNCHRONIZATION OF NORMAL FLOW FRAMEWORK PROTECTED BY HEADER ERROR CONTROL IN PASSIVE OPTICAL NETWORK OF TEN GIGABITS
    US8781321B2|2014-07-15|Gigabit passive optical network transmission convergence extension for next generation access
    ES2546060T3|2015-09-18|Method and apparatus for configuring an updated bandwidth map for a 10 gigabit passive optical network
    ES2883407T3|2021-12-07|Frame alignment in a PON
    US8929396B2|2015-01-06|Ethernet media access control organization specific extension
    WO2011050529A1|2011-05-05|Method for transmitting downlink frames in optical network and related apparatus thereof
    WO2017113349A1|2017-07-06|Data parsing and data transmission method and apparatus
    AU2013251220B2|2014-10-30|Method and apparatus for configuring upgraded bandwidth map for ten gigabit passive optical network
    同族专利:
    公开号 | 公开日
    AU2010333484B2|2014-03-06|
    CN102549954A|2012-07-04|
    CN102549954B|2014-11-05|
    JP2013514683A|2013-04-25|
    AU2010333484A1|2012-07-12|
    CA2784543A1|2011-06-23|
    ES2552833T3|2015-12-02|
    MX2012006957A|2012-07-30|
    EP2499770B1|2015-08-19|
    US20130272706A1|2013-10-17|
    CN104363531A|2015-02-18|
    EP2955868B1|2018-06-06|
    RU2531874C2|2014-10-27|
    BR112012014620A2|2016-03-01|
    EP2499770A4|2012-10-03|
    EP3447947A1|2019-02-27|
    HUE040203T2|2019-02-28|
    US8483563B2|2013-07-09|
    KR20120089361A|2012-08-09|
    PL2499770T3|2016-01-29|
    RU2012130006A|2014-01-27|
    CA2784543C|2015-06-23|
    US20110142437A1|2011-06-16|
    ES2686703T3|2018-10-19|
    WO2011072578A1|2011-06-23|
    KR101358768B1|2014-02-05|
    CN104363531B|2018-03-09|
    EP2955868A1|2015-12-16|
    JP5669030B2|2015-02-12|
    PL2955868T3|2018-11-30|
    EP2499770A1|2012-09-19|
    US8724994B2|2014-05-13|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US9026A|1852-06-15|Improvement in imitation stone |
    KR100601627B1|1999-11-26|2006-07-14|삼성전자주식회사|Decoding apparatus and method of receiving data packet from bluetooth baseband|
    EP1365548A1|2002-05-21|2003-11-26|Alcatel|Method for encapsulating variable length packets, and related data packet encapsulator and decapsulator|
    KR20040010931A|2002-07-25|2004-02-05|삼성전자주식회사|Generic Framing Procedure Frame Delineation Detection Circuit in communication system|
    KR100594028B1|2003-04-15|2006-07-03|삼성전자주식회사|GTC Frame Structure for Transmitting OMCI in GPON and Transmitting Method|
    JP2006101061A|2004-09-29|2006-04-13|Toyota Industries Corp|Communication method|
    RU2310278C1|2006-01-27|2007-11-10|Александр Геннадьевич Попов|Passive fiber-optic network|
    CN100558027C|2006-03-29|2009-11-04|华为技术有限公司|Simplify the method and system that the Gigabit Passive Optical Network downlink forward error correction is handled|
    JP4168059B2|2006-04-10|2008-10-22|株式会社日立コミュニケーションテクノロジー|PON system and station side device|
    CN101047470A|2006-05-17|2007-10-03|华为技术有限公司|Allocation method for forward error correction function in passive optical network|
    CN101436917B|2007-11-12|2012-06-27|华为技术有限公司|Method and apparatus for encoding and decoding data|
    JP5114268B2|2008-03-31|2013-01-09|株式会社日立製作所|Passive optical network system and operation method thereof|
    US8351785B2|2008-04-21|2013-01-08|Futurewei Technologies, Inc.|Gigabit passive optical network transmission convergence extension for next generation access|
    CN101374035B|2008-09-19|2012-09-05|中兴通讯股份有限公司|Decoding method and system for GBIT passive optical network and framing method|
    CN101409708A|2008-11-08|2009-04-15|浙江工业大学|GPON GTC frame-forming sublayer based on FPGA|
    US8483563B2|2009-12-16|2013-07-09|Futurewei Technologies, Inc.|Header error control protected ten gigabit passive optical network downstream frame synchronization pattern|
    US9209897B2|2011-12-20|2015-12-08|Broadcom Corporation|Adaptive forward error correction in passive optical networks|US8483563B2|2009-12-16|2013-07-09|Futurewei Technologies, Inc.|Header error control protected ten gigabit passive optical network downstream frame synchronization pattern|
    CN102195738B|2010-03-02|2015-06-10|中兴通讯股份有限公司|Synchronous processing method and device for downlink frames of GPONsystem|
    US8522116B2|2010-08-04|2013-08-27|Marvell IsraelLtd.|Systems and methods for performing forward error correction|
    KR20120073869A|2010-12-27|2012-07-05|한국전자통신연구원|Method for transmitting oam message and processing error in pon system|
    US9209897B2|2011-12-20|2015-12-08|Broadcom Corporation|Adaptive forward error correction in passive optical networks|
    US9280507B2|2012-10-22|2016-03-08|Intel Corporation|High performance interconnect physical layer|
    US9413484B2|2012-11-05|2016-08-09|Futurewei Technologies, Inc.|System and method for passive optical network communication|
    CN105027451B|2013-02-25|2018-01-26|中兴通讯公司|The method and apparatus of downlink forward error correction switch control in XG PON1 and NG PON2 TWDM PON systems|
    CN103532854B|2013-10-22|2017-05-10|迈普通信技术股份有限公司|Storage and forwarding method and device of message|
    KR101506207B1|2013-10-24|2015-03-26|라이트웍스 주식회사|Method for comprising bch code for giga bit passive optical network and method for reading thereof|
    KR101555976B1|2013-10-29|2015-09-30|라이트웍스 주식회사|Method for comprising physical frame for giga bit passive optical network|
    US9654250B2|2014-11-10|2017-05-16|Futurewei Technologies, Inc.|Adding operations, administration, and maintenanceinformation in 66-bit code|
    EP3086498A1|2015-04-24|2016-10-26|Alcatel Lucent|A method and an apparatus for generating a second data packet from a first data packet|
    US20170302433A1|2015-05-15|2017-10-19|Alcatel-Lucent Usa Inc.|Method And Apparatus For Time Transport In A Communication Network|
    EP3160074B1|2015-10-22|2021-03-17|Alcatel Lucent|Method and apparatus for transmitting control messages in an optical transmission network|
    CN106851439B|2015-12-07|2020-04-24|深圳市中兴微电子技术有限公司|Access method and device for multiple optical network units|
    US20190089785A1|2016-03-03|2019-03-21|Cadami GmbH|Identification encoding device and identification decoding device for data distribution and networks, and network elements comprising such devices|
    KR101696926B1|2016-05-27|2017-01-17|라이트웍스 주식회사|Frame synchronizing apparatus for passive optical network and method thereof|
    CN111800225A|2016-12-09|2020-10-20|华为技术有限公司|Data transmission method and equipment|
    JP2018191166A|2017-05-09|2018-11-29|富士通株式会社|Transmission device, reception device, transmission method, and reception method|
    EP3641416A4|2017-06-16|2021-03-31|Beijing Xiaomi Mobile Software Co., Ltd.|Method and device for determining time of transmitting synchronization block, , user equipment and base station|
    CN110149148B|2018-02-13|2022-02-25|颖飞公司|Communication system and optical transceiver device|
    WO2020142726A1|2019-01-04|2020-07-09|Futurewei Technologies, Inc.|Passive optical networksynchronization and clock recovery|
    CN110324115B|2019-06-10|2022-01-04|普联技术有限公司|Data transmission method and device, storage medium and terminal equipment|
    CN112511914A|2020-01-22|2021-03-16|中兴通讯股份有限公司|State switching method, device, equipment and storage medium|
    CN113382319A|2020-03-09|2021-09-10|华为技术有限公司|Data processing method and equipment|
    CN113993009A|2020-07-27|2022-01-28|上海诺基亚贝尔股份有限公司|Method and device for multi-domain transmission by time synchronization, OLT and ONU|
    法律状态:
    2018-03-27| B15K| Others concerning applications: alteration of classification|Ipc: H04B 10/27 (2013.01), H04J 3/06 (2006.01), H04L 1/ |
    2019-01-08| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2019-12-24| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2021-03-02| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2021-03-30| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 10 (DEZ) ANOS CONTADOS A PARTIR DE 30/03/2021, OBSERVADAS AS CONDICOES LEGAIS. |
    2021-05-04| B15G| Petition not considered as such [chapter 15.7 patent gazette]|
    2021-07-06| B12F| Other appeals [chapter 12.6 patent gazette]|Free format text: RECURSO: 870210058282 - 28/06/2021 |
    优先权:
    申请号 | 申请日 | 专利标题
    US28702409P| true| 2009-12-16|2009-12-16|
    US61/287,024|2009-12-16|
    US12/884,566|2010-09-17|
    US12/884,566|US8483563B2|2009-12-16|2010-09-17|Header error control protected ten gigabit passive optical network downstream frame synchronization pattern|
    PCT/CN2010/079453|WO2011072578A1|2009-12-16|2010-12-06|Downstream frame synchronization pattern protected by header error control in ten gigabit passive optical network|
    [返回顶部]